Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19cdd7d15ea24978bf815cd2a3979afab8df2beb3562e12027d10f9d83392b7a

Tx prefix hash: c8f334e9b2785ef668af7f8a3e6ec8169640f162528594c958801dfb1d04a151
Tx public key: 3bf67646319de6916e94e2c46ebbdca8bb70e97d5e557fe74a31c802bf5c26d9
Timestamp: 1729266833 Timestamp [UCT]: 2024-10-18 15:53:53 Age [y:d:h:m:s]: 00:036:22:04:31
Block: 1134381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26352 RingCT/type: yes/0
Extra: 013bf67646319de6916e94e2c46ebbdca8bb70e97d5e557fe74a31c802bf5c26d90211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f5a1a4b5f53388ccf77b8bcd8673a22086a0116fd8da8d9bf664740e8e16fa0 0.600000000000 1617680 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": 1134391, "vin": [ { "gen": { "height": 1134381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f5a1a4b5f53388ccf77b8bcd8673a22086a0116fd8da8d9bf664740e8e16fa0" } } ], "extra": [ 1, 59, 246, 118, 70, 49, 157, 230, 145, 110, 148, 226, 196, 110, 187, 220, 168, 187, 112, 233, 125, 94, 85, 127, 231, 74, 49, 200, 2, 191, 92, 38, 217, 2, 17, 0, 0, 0, 6, 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