Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bffeb9016dce25b5425301a73d5f9b765d81112fe8c412e0cc9fd3fed6a6a7d

Tx prefix hash: 024be5dd729de5061fc13f752e3ce0e92cbf021f27af0524ff75c144a34cb06f
Tx public key: 812c0b7d155c01126eee1b952598ac180feb8828846582ec22e74f7a905913d4
Timestamp: 1702582523 Timestamp [UCT]: 2023-12-14 19:35:23 Age [y:d:h:m:s]: 01:180:18:27:18
Block: 913150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390346 RingCT/type: yes/0
Extra: 01812c0b7d155c01126eee1b952598ac180feb8828846582ec22e74f7a905913d4021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b613bbbef444514cafbd354b9d19f23d1f7a95cbde327dbe9eb2622cce005d78 0.600000000000 1370396 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": 913160, "vin": [ { "gen": { "height": 913150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b613bbbef444514cafbd354b9d19f23d1f7a95cbde327dbe9eb2622cce005d78" } } ], "extra": [ 1, 129, 44, 11, 125, 21, 92, 1, 18, 110, 238, 27, 149, 37, 152, 172, 24, 15, 235, 136, 40, 132, 101, 130, 236, 34, 231, 79, 122, 144, 89, 19, 212, 2, 17, 0, 0, 0, 4, 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