Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea6c072f778c58758acfa61254e363469c5fa319023e7f8e60cb46f99c588efa

Tx prefix hash: ce265078396bdc08ae0a1fb79e7746e3d0e8d951a7f4a857abccaba436e3bc5b
Tx public key: fcc3f39fc816df52969d663d159b0be793b380f18efced8133d3cb0214dd07be
Timestamp: 1709398930 Timestamp [UCT]: 2024-03-02 17:02:10 Age [y:d:h:m:s]: 01:036:14:42:12
Block: 969673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287160 RingCT/type: yes/0
Extra: 01fcc3f39fc816df52969d663d159b0be793b380f18efced8133d3cb0214dd07be0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57caf15ea85ceacf7831912c836a561ae5dee9c4d4b524bb276293e41284c445 0.600000000000 1429510 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": 969683, "vin": [ { "gen": { "height": 969673 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57caf15ea85ceacf7831912c836a561ae5dee9c4d4b524bb276293e41284c445" } } ], "extra": [ 1, 252, 195, 243, 159, 200, 22, 223, 82, 150, 157, 102, 61, 21, 155, 11, 231, 147, 179, 128, 241, 142, 252, 237, 129, 51, 211, 203, 2, 20, 221, 7, 190, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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