Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e033bf1a5abafbd3746a97297bbd573c52d671a64951329c01267315c264bd27

Tx prefix hash: ab9fd89d891b8114b64760a32defa0e03b82115f320050addb755583e8e89054
Tx public key: b8ae8aa3c514e4d8a063e217da01fec8adb6ffba1c23b0636f3777ab005f96d4
Timestamp: 1706921314 Timestamp [UCT]: 2024-02-03 00:48:34 Age [y:d:h:m:s]: 01:027:09:39:06
Block: 949113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280621 RingCT/type: yes/0
Extra: 01b8ae8aa3c514e4d8a063e217da01fec8adb6ffba1c23b0636f3777ab005f96d40211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65a932cbdb169fd59ecf5699d76a623feb14ccc514f3ea6911a5dbbd5e821491 0.600000000000 1407635 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": 949123, "vin": [ { "gen": { "height": 949113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65a932cbdb169fd59ecf5699d76a623feb14ccc514f3ea6911a5dbbd5e821491" } } ], "extra": [ 1, 184, 174, 138, 163, 197, 20, 228, 216, 160, 99, 226, 23, 218, 1, 254, 200, 173, 182, 255, 186, 28, 35, 176, 99, 111, 55, 119, 171, 0, 95, 150, 212, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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