Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0430bc1a0241bba7f88d70f2fab21a95387b168077c1c404dfb4a9d943f901c8

Tx prefix hash: 73bebd74c96cdba2f9d676df516cd7665d70730e94d859c28b0da48e08b6ab64
Tx public key: 828b275bce36431684e8d4ebc272fd306df1bc99dcbee3108992d0283fb452ff
Timestamp: 1735366897 Timestamp [UCT]: 2024-12-28 06:21:37 Age [y:d:h:m:s]: 00:166:07:33:04
Block: 1184826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118660 RingCT/type: yes/0
Extra: 01828b275bce36431684e8d4ebc272fd306df1bc99dcbee3108992d0283fb452ff0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 482d41503b3b833e39dcbe94c4bdd834386cba29f35a6224b96575b46da8a626 0.600000000000 1671285 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": 1184836, "vin": [ { "gen": { "height": 1184826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "482d41503b3b833e39dcbe94c4bdd834386cba29f35a6224b96575b46da8a626" } } ], "extra": [ 1, 130, 139, 39, 91, 206, 54, 67, 22, 132, 232, 212, 235, 194, 114, 253, 48, 109, 241, 188, 153, 220, 190, 227, 16, 137, 146, 208, 40, 63, 180, 82, 255, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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