Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73faea867b93e011989e1a45583275e42049b7e1aa7291542b19a8dbfba57d0f

Tx prefix hash: f5c44c5e655da606255a1768d3aed1afd19ab9b2c903be922a0921722b14419c
Tx public key: dd06b88a3f13e62310049f95d061c30a40e9f1ab7018df9e2c94c3c1d7af9e00
Timestamp: 1705457719 Timestamp [UCT]: 2024-01-17 02:15:19 Age [y:d:h:m:s]: 01:294:04:13:24
Block: 936962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469063 RingCT/type: yes/0
Extra: 01dd06b88a3f13e62310049f95d061c30a40e9f1ab7018df9e2c94c3c1d7af9e0002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1aed3e95f919b64ae43d3cf3c362ae7c03962375127bb5e3fe1e877099ab283 0.600000000000 1395006 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": 936972, "vin": [ { "gen": { "height": 936962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1aed3e95f919b64ae43d3cf3c362ae7c03962375127bb5e3fe1e877099ab283" } } ], "extra": [ 1, 221, 6, 184, 138, 63, 19, 230, 35, 16, 4, 159, 149, 208, 97, 195, 10, 64, 233, 241, 171, 112, 24, 223, 158, 44, 148, 195, 193, 215, 175, 158, 0, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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