Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 620b89a686f04e1dd605256f43f8d36cf723f70daf92a9c3f5758345c3b71ba3

Tx prefix hash: 59281f94f1ea39ca309f548205dbcb27b1ab1e7ae061b5ce78ef11840054a0bc
Tx public key: bcfa703e73a42caf36e89bfa90177f984803b45d965080f9464f4fb14f979b13
Timestamp: 1706475933 Timestamp [UCT]: 2024-01-28 21:05:33 Age [y:d:h:m:s]: 01:029:00:59:29
Block: 945412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281814 RingCT/type: yes/0
Extra: 01bcfa703e73a42caf36e89bfa90177f984803b45d965080f9464f4fb14f979b130211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5de03f92caaa4de8ecc7c1c5648cbf0e0f481d2ecccbfadc55c7b71277085c7e 0.600000000000 1403726 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": 945422, "vin": [ { "gen": { "height": 945412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5de03f92caaa4de8ecc7c1c5648cbf0e0f481d2ecccbfadc55c7b71277085c7e" } } ], "extra": [ 1, 188, 250, 112, 62, 115, 164, 44, 175, 54, 232, 155, 250, 144, 23, 127, 152, 72, 3, 180, 93, 150, 80, 128, 249, 70, 79, 79, 177, 79, 151, 155, 19, 2, 17, 0, 0, 0, 5, 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