Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17729e2156768550e9ddd698d8837a1faefd7fdb3104eaaf8f4bab2914da101f

Tx prefix hash: e3acc5ce82d792332f7995334bfad596bc348979f0a81f22916be2abd7910d2d
Tx public key: 46730d4f82ee3f8a171ebf61ad3edf2f9d8818e73ba3f3427f1aa1a718b81fcd
Timestamp: 1707220734 Timestamp [UCT]: 2024-02-06 11:58:54 Age [y:d:h:m:s]: 00:278:18:01:18
Block: 951597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199584 RingCT/type: yes/0
Extra: 0146730d4f82ee3f8a171ebf61ad3edf2f9d8818e73ba3f3427f1aa1a718b81fcd0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44412fda5c74d4cf279e3ffc4c0dda844167d7d485a6ea935dbcc105503588c1 0.600000000000 1410379 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": 951607, "vin": [ { "gen": { "height": 951597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44412fda5c74d4cf279e3ffc4c0dda844167d7d485a6ea935dbcc105503588c1" } } ], "extra": [ 1, 70, 115, 13, 79, 130, 238, 63, 138, 23, 30, 191, 97, 173, 62, 223, 47, 157, 136, 24, 231, 59, 163, 243, 66, 127, 26, 161, 167, 24, 184, 31, 205, 2, 17, 0, 0, 0, 1, 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