Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a6b5a077a2ab8111508ce24a2694b1192a1f8f281ff919437193d8b8aef69c1

Tx prefix hash: 7e2a5e016789f7fd69724d83934f0d4d85e21a800a532b2a06aed3ad1fe57b05
Tx public key: 6275874847d21bacc847e92ce139bbb4384d37d3520c505045fbcb9d607a18a0
Timestamp: 1722466455 Timestamp [UCT]: 2024-07-31 22:54:15 Age [y:d:h:m:s]: 00:270:22:54:26
Block: 1077996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193581 RingCT/type: yes/0
Extra: 016275874847d21bacc847e92ce139bbb4384d37d3520c505045fbcb9d607a18a002110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb31a1cd2f3347962af613e29c32908850346c40f1a1a2004cbf914fd2418b3a 0.600000000000 1550551 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": 1078006, "vin": [ { "gen": { "height": 1077996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb31a1cd2f3347962af613e29c32908850346c40f1a1a2004cbf914fd2418b3a" } } ], "extra": [ 1, 98, 117, 135, 72, 71, 210, 27, 172, 200, 71, 233, 44, 225, 57, 187, 180, 56, 77, 55, 211, 82, 12, 80, 80, 69, 251, 203, 157, 96, 122, 24, 160, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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