Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a471499fe0e7b3cd1be8ca51a7e36ee137af63cf7522eec1051a0daae1a00000

Tx prefix hash: 79910db6f5918e1fc1b0f82f84de45fbf2e2ae588784b9db7cfa0eb16bbe136b
Tx public key: 8868c353a82f5d4e05c5228e53ff0fdcc5deafe8c4c6e3142c4fe2edd5fa6082
Timestamp: 1720784560 Timestamp [UCT]: 2024-07-12 11:42:40 Age [y:d:h:m:s]: 00:134:20:24:10
Block: 1064076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96479 RingCT/type: yes/0
Extra: 018868c353a82f5d4e05c5228e53ff0fdcc5deafe8c4c6e3142c4fe2edd5fa608202110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea78a0041b0f26589b3648809c74c60af72b5a3c922029003c6cc4c942cfae6d 0.600000000000 1534599 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": 1064086, "vin": [ { "gen": { "height": 1064076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea78a0041b0f26589b3648809c74c60af72b5a3c922029003c6cc4c942cfae6d" } } ], "extra": [ 1, 136, 104, 195, 83, 168, 47, 93, 78, 5, 197, 34, 142, 83, 255, 15, 220, 197, 222, 175, 232, 196, 198, 227, 20, 44, 79, 226, 237, 213, 250, 96, 130, 2, 17, 0, 0, 0, 1, 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