Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4829e6c2ee5efd271927b47d4baf1e007be6671190aa84814e6c159f83d37e7a

Tx prefix hash: b377adbcbca40af8b832a0b211bdcace696c90007d1b875f774d5c63180f4984
Tx public key: 42c17420969111d6c1dac6dd269ae9e00723341bdf6afcb05418989abd1a9c57
Timestamp: 1726133303 Timestamp [UCT]: 2024-09-12 09:28:23 Age [y:d:h:m:s]: 00:101:08:59:13
Block: 1108395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72531 RingCT/type: yes/0
Extra: 0142c17420969111d6c1dac6dd269ae9e00723341bdf6afcb05418989abd1a9c5702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3599f130495feea495a7de6570f5001fd263381b2e34e1efd9b17e2c67ecc0e 0.600000000000 1586278 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": 1108405, "vin": [ { "gen": { "height": 1108395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3599f130495feea495a7de6570f5001fd263381b2e34e1efd9b17e2c67ecc0e" } } ], "extra": [ 1, 66, 193, 116, 32, 150, 145, 17, 214, 193, 218, 198, 221, 38, 154, 233, 224, 7, 35, 52, 27, 223, 106, 252, 176, 84, 24, 152, 154, 189, 26, 156, 87, 2, 17, 0, 0, 0, 6, 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