Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 614dc9aef57302e09232eec0d082571e030324b4ed86bc54359f77222b528b19

Tx prefix hash: d945ab7a33d1964beae0c2ffc5d8790754c053778ed69b2c7f722c5686dbf3f2
Tx public key: fc35ea998d27b5ad4b0d95c40804d1ed544641b6a8ec4a7b1aae5c3a811eac70
Timestamp: 1708951601 Timestamp [UCT]: 2024-02-26 12:46:41 Age [y:d:h:m:s]: 01:044:10:03:12
Block: 965966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292752 RingCT/type: yes/0
Extra: 01fc35ea998d27b5ad4b0d95c40804d1ed544641b6a8ec4a7b1aae5c3a811eac7002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f521a09f0b4b3cc8c18aaa939d7bd286df02830ca626661e0cbcfd7bd7ec7cc 0.600000000000 1425721 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": 965976, "vin": [ { "gen": { "height": 965966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f521a09f0b4b3cc8c18aaa939d7bd286df02830ca626661e0cbcfd7bd7ec7cc" } } ], "extra": [ 1, 252, 53, 234, 153, 141, 39, 181, 173, 75, 13, 149, 196, 8, 4, 209, 237, 84, 70, 65, 182, 168, 236, 74, 123, 26, 174, 92, 58, 129, 30, 172, 112, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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