Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05d5471734f47ae4249657ae5f1f62d12bb4ab0389adcd249b4aa7df3750de10

Tx prefix hash: 402879afdd34a44a6317d501ea1900287d592f7a74929d2988e9ed6e8125bee3
Tx public key: 5e0b0ebf0bddc0afd727442f7206b1582243ea9bc9bac5e666f0236e40c0c3dd
Timestamp: 1706874412 Timestamp [UCT]: 2024-02-02 11:46:52 Age [y:d:h:m:s]: 01:272:03:41:05
Block: 948734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453278 RingCT/type: yes/0
Extra: 015e0b0ebf0bddc0afd727442f7206b1582243ea9bc9bac5e666f0236e40c0c3dd02110000000210a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f223728f370514f92f4111702d7b40f027aae4b2d19810294f338fc895cdb28 0.600000000000 1407204 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": 948744, "vin": [ { "gen": { "height": 948734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f223728f370514f92f4111702d7b40f027aae4b2d19810294f338fc895cdb28" } } ], "extra": [ 1, 94, 11, 14, 191, 11, 221, 192, 175, 215, 39, 68, 47, 114, 6, 177, 88, 34, 67, 234, 155, 201, 186, 197, 230, 102, 240, 35, 110, 64, 192, 195, 221, 2, 17, 0, 0, 0, 2, 16, 161, 116, 143, 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