Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e192d8e7dcf7d215d60cf1f5b5a70705c22a2233abe6f44491c8403526e9424

Tx prefix hash: e3372b538dbfeb0eff0dad6a286cc07085926bb02c286ff07ca9b8df070b928e
Tx public key: b0e0eaac30c004c5e9c5bbe9e417f699fe90f4582c8b102e55a44fbbbff56123
Timestamp: 1737189066 Timestamp [UCT]: 2025-01-18 08:31:06 Age [y:d:h:m:s]: 00:057:15:10:24
Block: 1199912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40973 RingCT/type: yes/0
Extra: 01b0e0eaac30c004c5e9c5bbe9e417f699fe90f4582c8b102e55a44fbbbff561230211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bfe0940622de682b38cf710261447b93968d76a35da0e3eba7e55507b275e69 0.600000000000 1686549 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": 1199922, "vin": [ { "gen": { "height": 1199912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bfe0940622de682b38cf710261447b93968d76a35da0e3eba7e55507b275e69" } } ], "extra": [ 1, 176, 224, 234, 172, 48, 192, 4, 197, 233, 197, 187, 233, 228, 23, 246, 153, 254, 144, 244, 88, 44, 139, 16, 46, 85, 164, 79, 187, 191, 245, 97, 35, 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