Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb6e887085586e9c020de5fabd5b91530c6556083ca42652a9c553d0bede65bd

Tx prefix hash: 83447c7f51bce6c3d800d8297301f819dd82661a18f09c45540ddc487d958416
Tx public key: ebdc67d3fe96c19d0d538bb64f6d6eec7d6d9fccc0db9c8e36040cbd86adc0ae
Timestamp: 1727773957 Timestamp [UCT]: 2024-10-01 09:12:37 Age [y:d:h:m:s]: 01:051:13:59:38
Block: 1122010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295256 RingCT/type: yes/0
Extra: 01ebdc67d3fe96c19d0d538bb64f6d6eec7d6d9fccc0db9c8e36040cbd86adc0ae02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fecc97f5888ecdb78bcb04d14d2fa2e60789db4c2c8662de5d44277b1025d182 0.600000000000 1604375 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": 1122020, "vin": [ { "gen": { "height": 1122010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fecc97f5888ecdb78bcb04d14d2fa2e60789db4c2c8662de5d44277b1025d182" } } ], "extra": [ 1, 235, 220, 103, 211, 254, 150, 193, 157, 13, 83, 139, 182, 79, 109, 110, 236, 125, 109, 159, 204, 192, 219, 156, 142, 54, 4, 12, 189, 134, 173, 192, 174, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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