Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7138817f6cc15f56bae72e5ffd2629822dc1cccf9f028b037b6d96f8f154583

Tx prefix hash: e0f701f2caf38134a691703d0cd1178d4b4ce57294479f39abe4953f1fff0c94
Tx public key: 16477fb4b264a515dd193d19d74e94c1a2f33ba430a90a8fe2f87110bffd487b
Timestamp: 1729555497 Timestamp [UCT]: 2024-10-22 00:04:57 Age [y:d:h:m:s]: 00:202:22:48:51
Block: 1136736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144876 RingCT/type: yes/0
Extra: 0116477fb4b264a515dd193d19d74e94c1a2f33ba430a90a8fe2f87110bffd487b021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1909766aa52f1a9c0f84f0724873c6806bf7645535b84939b1e1892acbcc025 0.600000000000 1620097 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": 1136746, "vin": [ { "gen": { "height": 1136736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1909766aa52f1a9c0f84f0724873c6806bf7645535b84939b1e1892acbcc025" } } ], "extra": [ 1, 22, 71, 127, 180, 178, 100, 165, 21, 221, 25, 61, 25, 215, 78, 148, 193, 162, 243, 59, 164, 48, 169, 10, 143, 226, 248, 113, 16, 191, 253, 72, 123, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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