Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f2ff5a3adbc8d680fa001081fce210f44c291b0d74c70e541b9bc9c0b9f6816

Tx prefix hash: 89bad6498ab1008d49959d82d72fd5b662fdfe82326d571aa80e365664d3cd87
Tx public key: 908585dfe593ae1645937833f10a05e5ff2941e51bcba706cfc643de3d1e63d4
Timestamp: 1700099465 Timestamp [UCT]: 2023-11-16 01:51:05 Age [y:d:h:m:s]: 01:063:04:08:28
Block: 892568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306546 RingCT/type: yes/0
Extra: 01908585dfe593ae1645937833f10a05e5ff2941e51bcba706cfc643de3d1e63d4021100000001c5452960000000000000000000

1 output(s) for total of 0.676942355000 dcy

stealth address amount amount idx
00: 401b8ee53a0b991fb74153885bd0d73adf6de95078e238c1cad3a40da7d4c119 0.676942355000 1348687 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": 892578, "vin": [ { "gen": { "height": 892568 } } ], "vout": [ { "amount": 676942355, "target": { "key": "401b8ee53a0b991fb74153885bd0d73adf6de95078e238c1cad3a40da7d4c119" } } ], "extra": [ 1, 144, 133, 133, 223, 229, 147, 174, 22, 69, 147, 120, 51, 241, 10, 5, 229, 255, 41, 65, 229, 27, 203, 167, 6, 207, 198, 67, 222, 61, 30, 99, 212, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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