Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1b234e1378b41dc254bd618f72934a311fb5ac41a306a180ca0297b285fdcf21

Tx prefix hash: 1ccce12a7eb27dc6853b3d6a7f0ce1a10b88e1f4067da6ba165c1290b208682d
Tx public key: f688eac5b89d798fe9e40c0ee46b77591f2efaffe944a2042b27c53b3d7ab675
Timestamp: 1720015107 Timestamp [UCT]: 2024-07-03 13:58:27 Age [y:d:h:m:s]: 00:281:13:42:28
Block: 1057683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201188 RingCT/type: yes/0
Extra: 01f688eac5b89d798fe9e40c0ee46b77591f2efaffe944a2042b27c53b3d7ab6750211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c91d7d46d8a8d37d6fd7799e0ea44fe4358d3a873a1f588eeb0adce029cc37fe 0.600000000000 1528122 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1057693, "vin": [ { "gen": { "height": 1057683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c91d7d46d8a8d37d6fd7799e0ea44fe4358d3a873a1f588eeb0adce029cc37fe" } } ], "extra": [ 1, 246, 136, 234, 197, 184, 157, 121, 143, 233, 228, 12, 14, 228, 107, 119, 89, 31, 46, 250, 255, 233, 68, 162, 4, 43, 39, 197, 59, 61, 122, 182, 117, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8