Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 960d78656c697ff53d8f2764d9bba09be3bb9d76e7c9565ce1d5786351fea6e7

Tx prefix hash: 9f74a733c184bf82e630d3a2f532466e4fd546a0f112cdc2b52a66e26f4abbdc
Tx public key: fbbc5de1cd20ea054c83fa6017e76cb131577e1ddec5ccc75dcc037699af525e
Timestamp: 1713567208 Timestamp [UCT]: 2024-04-19 22:53:28 Age [y:d:h:m:s]: 01:200:00:24:18
Block: 1004208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401599 RingCT/type: yes/0
Extra: 01fbbc5de1cd20ea054c83fa6017e76cb131577e1ddec5ccc75dcc037699af525e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c24a2d8c4c99b69c06367406a43e5c15ff683ba4d5e29f32f86f0a80563393ee 0.600000000000 1464776 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": 1004218, "vin": [ { "gen": { "height": 1004208 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c24a2d8c4c99b69c06367406a43e5c15ff683ba4d5e29f32f86f0a80563393ee" } } ], "extra": [ 1, 251, 188, 93, 225, 205, 32, 234, 5, 76, 131, 250, 96, 23, 231, 108, 177, 49, 87, 126, 29, 222, 197, 204, 199, 93, 204, 3, 118, 153, 175, 82, 94, 2, 17, 0, 0, 0, 3, 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