Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa141d278ebd9d4ed417d1a49f6f91ebc94ea84e783bd44093bf632d982c60ce

Tx prefix hash: d2b9af1c09dc2b7e5bda4f0d25ffd254de2cb321e19caaf68c9c4a06d48887e2
Tx public key: 9a22f04fcabe0c0136dd2967cbe0e8d140199ed7775d33b744e4b4a62c553e91
Timestamp: 1734605167 Timestamp [UCT]: 2024-12-19 10:46:07 Age [y:d:h:m:s]: 00:103:04:09:24
Block: 1178546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73498 RingCT/type: yes/0
Extra: 019a22f04fcabe0c0136dd2967cbe0e8d140199ed7775d33b744e4b4a62c553e91021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b710daf55dc7105f10a896ec436ca099a662844e68f1ef39333919d9bebb08d 0.600000000000 1664933 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": 1178556, "vin": [ { "gen": { "height": 1178546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b710daf55dc7105f10a896ec436ca099a662844e68f1ef39333919d9bebb08d" } } ], "extra": [ 1, 154, 34, 240, 79, 202, 190, 12, 1, 54, 221, 41, 103, 203, 224, 232, 209, 64, 25, 158, 215, 119, 93, 51, 183, 68, 228, 180, 166, 44, 85, 62, 145, 2, 17, 0, 0, 0, 5, 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