Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed49120bbdc41e4c1b7fcb1834ee73c50f3d67e2fd0fea9a66ebc2209b491f2b

Tx prefix hash: cef76fa60a5989c5e3373b6586c3ba80e011a9f02c1e40e204ea12a680797b40
Tx public key: 0fe090b53e8793491918b0ce60147cb5f3ededed9c093be832050637e7bd0848
Timestamp: 1695956983 Timestamp [UCT]: 2023-09-29 03:09:43 Age [y:d:h:m:s]: 01:227:03:41:03
Block: 858436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423415 RingCT/type: yes/0
Extra: 010fe090b53e8793491918b0ce60147cb5f3ededed9c093be832050637e7bd08480211000000094b8f5122000000000000000000

1 output(s) for total of 0.878304732000 dcy

stealth address amount amount idx
00: f3f5dcf51b5b83c7c833c9aae7ea10fa8c294af2ed2675546bd1e288a7e1deb1 0.878304732000 1312610 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": 858446, "vin": [ { "gen": { "height": 858436 } } ], "vout": [ { "amount": 878304732, "target": { "key": "f3f5dcf51b5b83c7c833c9aae7ea10fa8c294af2ed2675546bd1e288a7e1deb1" } } ], "extra": [ 1, 15, 224, 144, 181, 62, 135, 147, 73, 25, 24, 176, 206, 96, 20, 124, 181, 243, 237, 237, 237, 156, 9, 59, 232, 50, 5, 6, 55, 231, 189, 8, 72, 2, 17, 0, 0, 0, 9, 75, 143, 81, 34, 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