Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8b77a05878738c4c437248c2f1d9b23fdc1c27e52f001ed053b923b3454621d

Tx prefix hash: ca6495364882e65aa48217782abcd8480f498e7200f896b79d8f1ca55f92c36e
Tx public key: 48e575a6a37b743da7919ab050c26338e5647985ca6d7003fc21f8785c6fe460
Timestamp: 1635932555 Timestamp [UCT]: 2021-11-03 09:42:35 Age [y:d:h:m:s]: 03:063:17:22:42
Block: 366388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 824075 RingCT/type: yes/0
Extra: 0148e575a6a37b743da7919ab050c26338e5647985ca6d7003fc21f8785c6fe460021100000008a272b9cb000000000000000000

1 output(s) for total of 37.499809902000 dcy

stealth address amount amount idx
00: b1b8ed7139bc2aaeac68e0762a3c9c55ff91f610683d0d501bdf0a150b1446c9 37.499809902000 743764 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": 366398, "vin": [ { "gen": { "height": 366388 } } ], "vout": [ { "amount": 37499809902, "target": { "key": "b1b8ed7139bc2aaeac68e0762a3c9c55ff91f610683d0d501bdf0a150b1446c9" } } ], "extra": [ 1, 72, 229, 117, 166, 163, 123, 116, 61, 167, 145, 154, 176, 80, 194, 99, 56, 229, 100, 121, 133, 202, 109, 112, 3, 252, 33, 248, 120, 92, 111, 228, 96, 2, 17, 0, 0, 0, 8, 162, 114, 185, 203, 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