Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4226caadf072f5c45dd441d96d2751ba9866dd314c7667d40d1032bce9837a4

Tx prefix hash: 1599ec9cf20bf6dc64190e3467c54a8264aabf14488791979025c076d4359fba
Tx public key: 218b3651a3a80ecd447f5c1e29164fd1eb6da1ddd691f5a4e2868ab3ed72602a
Timestamp: 1714443363 Timestamp [UCT]: 2024-04-30 02:16:03 Age [y:d:h:m:s]: 00:345:01:18:31
Block: 1011484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246668 RingCT/type: yes/0
Extra: 01218b3651a3a80ecd447f5c1e29164fd1eb6da1ddd691f5a4e2868ab3ed72602a0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 775b0a70ccc25c12295e596eff53c7210d95b5b747d0fbaf31388c866fa24c93 0.600000000000 1473726 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": 1011494, "vin": [ { "gen": { "height": 1011484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "775b0a70ccc25c12295e596eff53c7210d95b5b747d0fbaf31388c866fa24c93" } } ], "extra": [ 1, 33, 139, 54, 81, 163, 168, 14, 205, 68, 127, 92, 30, 41, 22, 79, 209, 235, 109, 161, 221, 214, 145, 245, 164, 226, 134, 138, 179, 237, 114, 96, 42, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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