Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71771ad3a09790008b5b80063d1607f3710116e6a263e263e8f644e36b6d63f7

Tx prefix hash: 7fdb4ee22d48b1d4f7398142110d39917b5638a07fea8c096c9a18171dcfb72f
Tx public key: 4f5659b465fbfed4c8fd8d79451375d682e00bbdd89457cacb58045eff3370f3
Timestamp: 1706609308 Timestamp [UCT]: 2024-01-30 10:08:28 Age [y:d:h:m:s]: 01:285:07:03:20
Block: 946525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 462692 RingCT/type: yes/0
Extra: 014f5659b465fbfed4c8fd8d79451375d682e00bbdd89457cacb58045eff3370f302110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c54d8904c969a69edcf50cfed4775a0db779d2e0e2cd3c2187f79138fb1e2e7b 0.600000000000 1404857 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": 946535, "vin": [ { "gen": { "height": 946525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c54d8904c969a69edcf50cfed4775a0db779d2e0e2cd3c2187f79138fb1e2e7b" } } ], "extra": [ 1, 79, 86, 89, 180, 101, 251, 254, 212, 200, 253, 141, 121, 69, 19, 117, 214, 130, 224, 11, 189, 216, 148, 87, 202, 203, 88, 4, 94, 255, 51, 112, 243, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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