Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dd5cb92472f8604e1b1ea586f862f9a875394f805a200c194782e717b9d7491

Tx prefix hash: a74a2e4928c0c5be50ecc100c86a537309149e902e8e47c182e047efa3dbaecd
Tx public key: 25845146abcc5f7fa78c66244715f564c3d7ab0cb88852752dc5a3d1173f3228
Timestamp: 1583076229 Timestamp [UCT]: 2020-03-01 15:23:49 Age [y:d:h:m:s]: 05:058:23:47:09
Block: 74503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196877 RingCT/type: yes/0
Extra: 0125845146abcc5f7fa78c66244715f564c3d7ab0cb88852752dc5a3d1173f32280211000000a303d36d11000000000000000000

1 output(s) for total of 347.649357694000 dcy

stealth address amount amount idx
00: f0a5738fb9998a93be7afd5e75d72271dadc978b2e94a8fff30aa412a1caec14 347.649357694000 137874 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": 74513, "vin": [ { "gen": { "height": 74503 } } ], "vout": [ { "amount": 347649357694, "target": { "key": "f0a5738fb9998a93be7afd5e75d72271dadc978b2e94a8fff30aa412a1caec14" } } ], "extra": [ 1, 37, 132, 81, 70, 171, 204, 95, 127, 167, 140, 102, 36, 71, 21, 245, 100, 195, 215, 171, 12, 184, 136, 82, 117, 45, 197, 163, 209, 23, 63, 50, 40, 2, 17, 0, 0, 0, 163, 3, 211, 109, 17, 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