Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c30f6ff56ded5dfe3f3a92ff5df5755a43833f8652ee0d38d3ae126a8650774

Tx prefix hash: 6f12654239a4d4d36a20d76043d67f1a377f8c960a2463ae8d0ace7dab0ac3ad
Tx public key: 903a50a299ea408145c3dbc1ea22d477e971e006956fbdd76ab7b336bed22f4f
Timestamp: 1717232159 Timestamp [UCT]: 2024-06-01 08:55:59 Age [y:d:h:m:s]: 00:348:16:36:19
Block: 1034619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249210 RingCT/type: yes/0
Extra: 01903a50a299ea408145c3dbc1ea22d477e971e006956fbdd76ab7b336bed22f4f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4f3632646f0f354fdcab5448ebafbb90f5c5fe09c00535b2524cc2ad4852cbb 0.600000000000 1503132 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": 1034629, "vin": [ { "gen": { "height": 1034619 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4f3632646f0f354fdcab5448ebafbb90f5c5fe09c00535b2524cc2ad4852cbb" } } ], "extra": [ 1, 144, 58, 80, 162, 153, 234, 64, 129, 69, 195, 219, 193, 234, 34, 212, 119, 233, 113, 224, 6, 149, 111, 189, 215, 106, 183, 179, 54, 190, 210, 47, 79, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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