Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64612b0024ac6fee3f9fb866bd8f5065948f8e84e71e24e760e0e9b7bfb6fcae

Tx prefix hash: fb3b2c4a9fb66f84a75355956f549236ee2e10aa4e536c3e950a094704f14656
Tx public key: b08a74167c8ea600d5c8437282a218323d90960e81873dc021f89dfde51d34ff
Timestamp: 1697825178 Timestamp [UCT]: 2023-10-20 18:06:18 Age [y:d:h:m:s]: 01:243:15:23:46
Block: 873915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435037 RingCT/type: yes/0
Extra: 01b08a74167c8ea600d5c8437282a218323d90960e81873dc021f89dfde51d34ff02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.780471138000 dcy

stealth address amount amount idx
00: 556171a319c9d5417b17aee5502e139ceb9c5eda1b4c89cb8b4c9b7963dac876 0.780471138000 1329101 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": 873925, "vin": [ { "gen": { "height": 873915 } } ], "vout": [ { "amount": 780471138, "target": { "key": "556171a319c9d5417b17aee5502e139ceb9c5eda1b4c89cb8b4c9b7963dac876" } } ], "extra": [ 1, 176, 138, 116, 22, 124, 142, 166, 0, 213, 200, 67, 114, 130, 162, 24, 50, 61, 144, 150, 14, 129, 135, 61, 192, 33, 248, 157, 253, 229, 29, 52, 255, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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