Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a966c4ddee3cc8ffd038e1803d030bb30fa547b2f30254f2f928fc8df220442e

Tx prefix hash: c220af777ce937191c6636bd5c68d5102d39c0b10557fc751918fcffd0ef6bbc
Tx public key: f1e807b894907b346aa6cec355dc21d99f0ac21324e2c6a18091b52190184ad0
Timestamp: 1732890444 Timestamp [UCT]: 2024-11-29 14:27:24 Age [y:d:h:m:s]: 00:353:04:49:19
Block: 1164333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249960 RingCT/type: yes/0
Extra: 01f1e807b894907b346aa6cec355dc21d99f0ac21324e2c6a18091b52190184ad00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26fd4ba5cd4456ff8fa7151d0ca0e7615f726ff2345a1e5cf4f2d378563c4a73 0.600000000000 1650006 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": 1164343, "vin": [ { "gen": { "height": 1164333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26fd4ba5cd4456ff8fa7151d0ca0e7615f726ff2345a1e5cf4f2d378563c4a73" } } ], "extra": [ 1, 241, 232, 7, 184, 148, 144, 123, 52, 106, 166, 206, 195, 85, 220, 33, 217, 159, 10, 194, 19, 36, 226, 198, 161, 128, 145, 181, 33, 144, 24, 74, 208, 2, 17, 0, 0, 0, 4, 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