Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 953758f34828ca72c00db148140240c7cd3c97c4aae00c8301f0722bc5fcfc00

Tx prefix hash: b223eb0dc50ace5b09e347d11d82b420beac5152e94d8426fd30c40a0ff584d1
Tx public key: 695de9bab0129fe8102575748db2a949cea45ea2f0b4c803fbfae1fb2a981c59
Timestamp: 1699482466 Timestamp [UCT]: 2023-11-08 22:27:46 Age [y:d:h:m:s]: 01:220:04:37:37
Block: 887459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418513 RingCT/type: yes/0
Extra: 01695de9bab0129fe8102575748db2a949cea45ea2f0b4c803fbfae1fb2a981c590211000000024b8f5122000000000000000000

1 output(s) for total of 0.703849705000 dcy

stealth address amount amount idx
00: 29bc2987267bf36641e46397f1a0f42f25159b4c6089b95b8ec67d3ecdcb362e 0.703849705000 1343342 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": 887469, "vin": [ { "gen": { "height": 887459 } } ], "vout": [ { "amount": 703849705, "target": { "key": "29bc2987267bf36641e46397f1a0f42f25159b4c6089b95b8ec67d3ecdcb362e" } } ], "extra": [ 1, 105, 93, 233, 186, 176, 18, 159, 232, 16, 37, 117, 116, 141, 178, 169, 73, 206, 164, 94, 162, 240, 180, 200, 3, 251, 250, 225, 251, 42, 152, 28, 89, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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