Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0495eb35958919333fe4778c20dd62d112c8d0c7806ae97f2b55e55d068f0860

Tx prefix hash: 6889df14b965d98c6c292671e80fc1e440bf9a09197e1e0ff017731717f4f3cc
Tx public key: 80eeffbf062716caa014ed0ffe12e44355f47ffd3b89f68aa39f03ead21b4568
Timestamp: 1699292074 Timestamp [UCT]: 2023-11-06 17:34:34 Age [y:d:h:m:s]: 01:189:06:14:49
Block: 885878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396485 RingCT/type: yes/0
Extra: 0180eeffbf062716caa014ed0ffe12e44355f47ffd3b89f68aa39f03ead21b456802110000000d4b8f5122000000000000000000

1 output(s) for total of 0.712391034000 dcy

stealth address amount amount idx
00: 8af646204d4cccb415b54a0c0cd7875226b38d2b04283ac1d933de6e022e2ead 0.712391034000 1341671 of 0

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": 885888, "vin": [ { "gen": { "height": 885878 } } ], "vout": [ { "amount": 712391034, "target": { "key": "8af646204d4cccb415b54a0c0cd7875226b38d2b04283ac1d933de6e022e2ead" } } ], "extra": [ 1, 128, 238, 255, 191, 6, 39, 22, 202, 160, 20, 237, 15, 254, 18, 228, 67, 85, 244, 127, 253, 59, 137, 246, 138, 163, 159, 3, 234, 210, 27, 69, 104, 2, 17, 0, 0, 0, 13, 75, 143, 81, 34, 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