Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcbe7c7c43ed5fcaaa9dc31f89e21278d030d8e347f6a6df7ef0c2f0e14a4e7d

Tx prefix hash: 4c9bdd840de784b8d946a14f2dfeef1e1ae57ba2ba264572658a14ace5add729
Tx public key: b5e850851495ebce0876aa6e5c2f4d2c6265e3165ae4f37acf0a2de8f1c6faf3
Timestamp: 1729860595 Timestamp [UCT]: 2024-10-25 12:49:55 Age [y:d:h:m:s]: 00:190:04:30:43
Block: 1139263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135748 RingCT/type: yes/0
Extra: 01b5e850851495ebce0876aa6e5c2f4d2c6265e3165ae4f37acf0a2de8f1c6faf30211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d13ee741bfdb9eddfc8396a365383dca246b6cd00f11269480f765ed181bb4e1 0.600000000000 1623046 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": 1139273, "vin": [ { "gen": { "height": 1139263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d13ee741bfdb9eddfc8396a365383dca246b6cd00f11269480f765ed181bb4e1" } } ], "extra": [ 1, 181, 232, 80, 133, 20, 149, 235, 206, 8, 118, 170, 110, 92, 47, 77, 44, 98, 101, 227, 22, 90, 228, 243, 122, 207, 10, 45, 232, 241, 198, 250, 243, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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