Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80f14f086deb5a81fa24689029f885a70c54820e16220131b2ef8b1f44a46e3b

Tx prefix hash: 9f8e87911681751d4788b9cf5fa0f85a9c57248494c87ba89b275ab1950a0fb4
Tx public key: bf34c8a9f2c9912c70b210e1f1f33cd54981122961b3c41ae626c38462e9df2d
Timestamp: 1648870140 Timestamp [UCT]: 2022-04-02 03:29:00 Age [y:d:h:m:s]: 02:347:22:33:49
Block: 471369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 768163 RingCT/type: yes/0
Extra: 01bf34c8a9f2c9912c70b210e1f1f33cd54981122961b3c41ae626c38462e9df2d0211000000054a0f5013000000000000000000

1 output(s) for total of 16.832905135000 dcy

stealth address amount amount idx
00: cbc526cf0fbd5131fd1b75e89a0b0f9484ddeed875fea6b9859e7d6977e98e13 16.832905135000 890697 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": 471379, "vin": [ { "gen": { "height": 471369 } } ], "vout": [ { "amount": 16832905135, "target": { "key": "cbc526cf0fbd5131fd1b75e89a0b0f9484ddeed875fea6b9859e7d6977e98e13" } } ], "extra": [ 1, 191, 52, 200, 169, 242, 201, 145, 44, 112, 178, 16, 225, 241, 243, 60, 213, 73, 129, 18, 41, 97, 179, 196, 26, 230, 38, 195, 132, 98, 233, 223, 45, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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