Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecc0ebd68fcbf89d9509f1ff49d363cbec99f41fd107a73a6458a1a29344f910

Tx prefix hash: cef75d001701e3aebc0b3bd6150e7dcd3fb5a0fae82d67b9d2b06c82f789ffd8
Tx public key: 084bec1894c0b7b7ee359b09ac174da4704a1a737bd0a74b839d61d47fa3806c
Timestamp: 1705046794 Timestamp [UCT]: 2024-01-12 08:06:34 Age [y:d:h:m:s]: 01:015:15:13:12
Block: 933567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272344 RingCT/type: yes/0
Extra: 01084bec1894c0b7b7ee359b09ac174da4704a1a737bd0a74b839d61d47fa3806c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a038d1d200c883e1891f3b13f031e570521c95b32e7142fd82e8d11fd920260 0.600000000000 1391531 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": 933577, "vin": [ { "gen": { "height": 933567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a038d1d200c883e1891f3b13f031e570521c95b32e7142fd82e8d11fd920260" } } ], "extra": [ 1, 8, 75, 236, 24, 148, 192, 183, 183, 238, 53, 155, 9, 172, 23, 77, 164, 112, 74, 26, 115, 123, 208, 167, 75, 131, 157, 97, 212, 127, 163, 128, 108, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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