Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18e1766bdb26d0fb3473c0577f163a94ad6c3134d305b1df6c020ac09b235058

Tx prefix hash: 4160c6297f78b3cc831a63122ca25711b11ff6c9939e97090cca401400d6a386
Tx public key: 8dc5e05bb69c7ba0b9687c89c8b21005a7ac5146bc8e763f75f898306b04f40b
Timestamp: 1709911294 Timestamp [UCT]: 2024-03-08 15:21:34 Age [y:d:h:m:s]: 01:099:18:43:01
Block: 973921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332241 RingCT/type: yes/0
Extra: 018dc5e05bb69c7ba0b9687c89c8b21005a7ac5146bc8e763f75f898306b04f40b02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59e7226e0cb8819d62337cf6f66055f94d799d3cfa86f11d6d47b2de941da4c1 0.600000000000 1433864 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": 973931, "vin": [ { "gen": { "height": 973921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59e7226e0cb8819d62337cf6f66055f94d799d3cfa86f11d6d47b2de941da4c1" } } ], "extra": [ 1, 141, 197, 224, 91, 182, 156, 123, 160, 185, 104, 124, 137, 200, 178, 16, 5, 167, 172, 81, 70, 188, 142, 118, 63, 117, 248, 152, 48, 107, 4, 244, 11, 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