Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04f67a58b76002dc9be18d436889c93d157b283e94401c23141c378bf5a1f264

Tx prefix hash: 759e91d802c4f2833c6e347b7c09e8c2dddf6d72b422961b5183a26069bbb4b3
Tx public key: e2b784f46e35c34a3619c466f42eaf5512f52ca55417981d4be1e36c10940ad2
Timestamp: 1577799056 Timestamp [UCT]: 2019-12-31 13:30:56 Age [y:d:h:m:s]: 04:333:15:10:22
Block: 35788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127530 RingCT/type: yes/0
Extra: 01e2b784f46e35c34a3619c466f42eaf5512f52ca55417981d4be1e36c10940ad202110000000ed81c26c0000000000000000000

1 output(s) for total of 467.111278450000 dcy

stealth address amount amount idx
00: fb1bb052d1f89ed0f2d598cfea5591fa6d33b2d94cb4f0d0f8873c79bc68d54f 467.111278450000 60418 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": 35798, "vin": [ { "gen": { "height": 35788 } } ], "vout": [ { "amount": 467111278450, "target": { "key": "fb1bb052d1f89ed0f2d598cfea5591fa6d33b2d94cb4f0d0f8873c79bc68d54f" } } ], "extra": [ 1, 226, 183, 132, 244, 110, 53, 195, 74, 54, 25, 196, 102, 244, 46, 175, 85, 18, 245, 44, 165, 84, 23, 152, 29, 75, 225, 227, 108, 16, 148, 10, 210, 2, 17, 0, 0, 0, 14, 216, 28, 38, 192, 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