Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aad28352d5de4c4eb497fd1a241ce2c9fba067470550931c44c5f2a2ee4bdfd6

Tx prefix hash: 92d2918f6ef82d19e02c929c199714139eb5a554ad0f5b00802ae2a3b0a2fd38
Tx public key: c56209e2aefcf7e00f6c7d0f6af359cb79969d404a5f169799741bc570638e57
Timestamp: 1640793054 Timestamp [UCT]: 2021-12-29 15:50:54 Age [y:d:h:m:s]: 03:008:19:26:27
Block: 406128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 785298 RingCT/type: yes/0
Extra: 01c56209e2aefcf7e00f6c7d0f6af359cb79969d404a5f169799741bc570638e57021100000002ed5d3ead000000000000000000

1 output(s) for total of 27.690429159000 dcy

stealth address amount amount idx
00: 1a9fd84ffc3b3550086435174561398de7ae5e9ad059b0405f65f01f627725ae 27.690429159000 806844 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": 406138, "vin": [ { "gen": { "height": 406128 } } ], "vout": [ { "amount": 27690429159, "target": { "key": "1a9fd84ffc3b3550086435174561398de7ae5e9ad059b0405f65f01f627725ae" } } ], "extra": [ 1, 197, 98, 9, 226, 174, 252, 247, 224, 15, 108, 125, 15, 106, 243, 89, 203, 121, 150, 157, 64, 74, 95, 22, 151, 153, 116, 27, 197, 112, 99, 142, 87, 2, 17, 0, 0, 0, 2, 237, 93, 62, 173, 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