Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 883e9b9c724c77b3c9ff4b01b9eecee9226fd77e1ecb7f733254ede564cdf42d

Tx prefix hash: b8c5df3ba88c832a0c21d31f92887a81e9f7f5b80bb141bf0d44d044e653dbb8
Tx public key: 34b3b05dc0687332452bf2bcb893a85a916ff830269b823aa3530446c415ca22
Timestamp: 1734469671 Timestamp [UCT]: 2024-12-17 21:07:51 Age [y:d:h:m:s]: 00:183:02:04:56
Block: 1177432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130532 RingCT/type: yes/0
Extra: 0134b3b05dc0687332452bf2bcb893a85a916ff830269b823aa3530446c415ca2202110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64d4451a94a687179c681b6e09e1fc19289838c4aef35ba75d7ad6671078cb39 0.600000000000 1663803 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": 1177442, "vin": [ { "gen": { "height": 1177432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64d4451a94a687179c681b6e09e1fc19289838c4aef35ba75d7ad6671078cb39" } } ], "extra": [ 1, 52, 179, 176, 93, 192, 104, 115, 50, 69, 43, 242, 188, 184, 147, 168, 90, 145, 111, 248, 48, 38, 155, 130, 58, 163, 83, 4, 70, 196, 21, 202, 34, 2, 17, 0, 0, 0, 10, 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