Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b3c3b0b09b876ed803826adb848b8c9bacbd98149d224f1d495d796425eb87f

Tx prefix hash: ec54af101bfec8f0ba31fea8ef43ceac3a6348b2186486f4113d48d353d4717f
Tx public key: a8694a9829a2ba5312b082c124f6a3f243564cc79f4e34f9c2db1c4577978172
Timestamp: 1730565501 Timestamp [UCT]: 2024-11-02 16:38:21 Age [y:d:h:m:s]: 00:226:05:57:39
Block: 1145062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161478 RingCT/type: yes/0
Extra: 01a8694a9829a2ba5312b082c124f6a3f243564cc79f4e34f9c2db1c45779781720211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3c421cb0dc30629ffb8f7a54ca61d9af62b7aac5b826de7394cdc0ddf72bbf8 0.600000000000 1629427 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": 1145072, "vin": [ { "gen": { "height": 1145062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c421cb0dc30629ffb8f7a54ca61d9af62b7aac5b826de7394cdc0ddf72bbf8" } } ], "extra": [ 1, 168, 105, 74, 152, 41, 162, 186, 83, 18, 176, 130, 193, 36, 246, 163, 242, 67, 86, 76, 199, 159, 78, 52, 249, 194, 219, 28, 69, 119, 151, 129, 114, 2, 17, 0, 0, 0, 2, 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