Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac294b8a5ff84a53584d13ef83bdaa572b122f007c39fac301269a891667d27d

Tx prefix hash: c8e7a0cc9c532550eb332078a8dfd47028abe5ba6e2ad1b34ca1a413ac2a8ab3
Tx public key: aa74b53434d43e25824ac8d7617bbe6dfa4a63d972b786f28676c6546e399abf
Timestamp: 1705619032 Timestamp [UCT]: 2024-01-18 23:03:52 Age [y:d:h:m:s]: 01:010:04:04:09
Block: 938309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268357 RingCT/type: yes/0
Extra: 01aa74b53434d43e25824ac8d7617bbe6dfa4a63d972b786f28676c6546e399abf02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ad91d305f43c3e93118fc6f83a120c443d8f935f0069c087f56474918f3e2aa 0.600000000000 1396379 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": 938319, "vin": [ { "gen": { "height": 938309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ad91d305f43c3e93118fc6f83a120c443d8f935f0069c087f56474918f3e2aa" } } ], "extra": [ 1, 170, 116, 181, 52, 52, 212, 62, 37, 130, 74, 200, 215, 97, 123, 190, 109, 250, 74, 99, 217, 114, 183, 134, 242, 134, 118, 198, 84, 110, 57, 154, 191, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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