Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1860616a742cf67908ab80de45a0d96f6b76cc55feb13668f7992c81dcc80ce2

Tx prefix hash: 84fdf0d62ea7eee96004148f15b7c7b5551ba7e54ff921c81fd1100bb9a0e8b3
Tx public key: eeb3f303564e3eba22fc78c1a80bf46bbc0ff8ae6e9d66c34f38dd7167dd66ae
Timestamp: 1699863415 Timestamp [UCT]: 2023-11-13 08:16:55 Age [y:d:h:m:s]: 01:139:22:25:40
Block: 890619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361181 RingCT/type: yes/0
Extra: 01eeb3f303564e3eba22fc78c1a80bf46bbc0ff8ae6e9d66c34f38dd7167dd66ae02110000002275e3f0e9000000000000000000

1 output(s) for total of 0.687083527000 dcy

stealth address amount amount idx
00: fea483e0f7d7f5068081c6bf32f6103f2abf556d1c246b6d38a1b58950a7ac6b 0.687083527000 1346644 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": 890629, "vin": [ { "gen": { "height": 890619 } } ], "vout": [ { "amount": 687083527, "target": { "key": "fea483e0f7d7f5068081c6bf32f6103f2abf556d1c246b6d38a1b58950a7ac6b" } } ], "extra": [ 1, 238, 179, 243, 3, 86, 78, 62, 186, 34, 252, 120, 193, 168, 11, 244, 107, 188, 15, 248, 174, 110, 157, 102, 195, 79, 56, 221, 113, 103, 221, 102, 174, 2, 17, 0, 0, 0, 34, 117, 227, 240, 233, 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