Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb1cc89715b6ee8110e4c4f2f728d6a13c7acb587f93d18643a9674e5313eb98

Tx prefix hash: e8f391077c73db2750de2a7feb2c768cb3168ebb7d73b5d1344ea2c9e3e90e77
Tx public key: e4d785aa0f3d14a3589d575705bcbae8de49fa2eb21feba206791ab247e50bec
Timestamp: 1697871406 Timestamp [UCT]: 2023-10-21 06:56:46 Age [y:d:h:m:s]: 01:354:02:40:33
Block: 874298 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511783 RingCT/type: yes/0
Extra: 01e4d785aa0f3d14a3589d575705bcbae8de49fa2eb21feba206791ab247e50bec02110000000de6d27f9c000000000000000000

1 output(s) for total of 0.778193876000 dcy

stealth address amount amount idx
00: 5b7c9a3f5e90e3ff4e243b67862b158df055183c310a09620c1a61d38b9376ea 0.778193876000 1329504 of 0

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": 874308, "vin": [ { "gen": { "height": 874298 } } ], "vout": [ { "amount": 778193876, "target": { "key": "5b7c9a3f5e90e3ff4e243b67862b158df055183c310a09620c1a61d38b9376ea" } } ], "extra": [ 1, 228, 215, 133, 170, 15, 61, 20, 163, 88, 157, 87, 87, 5, 188, 186, 232, 222, 73, 250, 46, 178, 31, 235, 162, 6, 121, 26, 178, 71, 229, 11, 236, 2, 17, 0, 0, 0, 13, 230, 210, 127, 156, 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