Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 807fad872b77ab262992e8366b377b0c42be29a2f49683af0b6fe233ed4bc3ca

Tx prefix hash: 74540a0b1b92f446bd6674abe4ec5acf16ce344f0888ccd2660249e5ce014701
Tx public key: b5a1dcfd8df2cd75aea7cdf87a3b2c06f04c159e3cdfffb258f22c5178b39084
Timestamp: 1701043672 Timestamp [UCT]: 2023-11-27 00:07:52 Age [y:d:h:m:s]: 01:202:03:57:04
Block: 900391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405602 RingCT/type: yes/0
Extra: 01b5a1dcfd8df2cd75aea7cdf87a3b2c06f04c159e3cdfffb258f22c5178b3908402110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.637721163000 dcy

stealth address amount amount idx
00: 5e4d205f538e827ae153b4b8ef7fa3b4ee4720b0533232741ff423aa1415af96 0.637721163000 1356892 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": 900401, "vin": [ { "gen": { "height": 900391 } } ], "vout": [ { "amount": 637721163, "target": { "key": "5e4d205f538e827ae153b4b8ef7fa3b4ee4720b0533232741ff423aa1415af96" } } ], "extra": [ 1, 181, 161, 220, 253, 141, 242, 205, 117, 174, 167, 205, 248, 122, 59, 44, 6, 240, 76, 21, 158, 60, 223, 255, 178, 88, 242, 44, 81, 120, 179, 144, 132, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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