Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fc5c50cd25f817b593378a66d5b34a997523efe89d1490865be86224f21bec6

Tx prefix hash: d806fa384b0981b464350a6dd9f9c94b5899a15a8cc4404ae0bc2b3c41f7fcbb
Tx public key: 0b56e944c229b26ea84a6bdcbd8ddcc975bba2052f85b3a072a38b87eb829522
Timestamp: 1728445593 Timestamp [UCT]: 2024-10-09 03:46:33 Age [y:d:h:m:s]: 00:170:05:57:36
Block: 1127570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121463 RingCT/type: yes/0
Extra: 010b56e944c229b26ea84a6bdcbd8ddcc975bba2052f85b3a072a38b87eb829522021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 574f4856a6988f2f96e386df72933c1f99b5c3f1a490940e5a880e1a875feec9 0.600000000000 1610377 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": 1127580, "vin": [ { "gen": { "height": 1127570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "574f4856a6988f2f96e386df72933c1f99b5c3f1a490940e5a880e1a875feec9" } } ], "extra": [ 1, 11, 86, 233, 68, 194, 41, 178, 110, 168, 74, 107, 220, 189, 141, 220, 201, 117, 187, 162, 5, 47, 133, 179, 160, 114, 163, 139, 135, 235, 130, 149, 34, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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