Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a110d9ace4ce8cd2fe43354e252e5c51caf5f400d37ba2b2af879bd7055ca25

Tx prefix hash: 5a1ee552081c9da312af9d1dafdcf3cb12666141539e79b86286dd1f62d62294
Tx public key: 52e98095c631573b7017fbf1a779cfe4fea3ada715154cce8ed9cfb7c73a5904
Timestamp: 1630909290 Timestamp [UCT]: 2021-09-06 06:21:30 Age [y:d:h:m:s]: 03:114:12:41:49
Block: 328384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 856816 RingCT/type: yes/0
Extra: 0152e98095c631573b7017fbf1a779cfe4fea3ada715154cce8ed9cfb7c73a59040211000000137062e8e6000000000000000000

1 output(s) for total of 50.110407934000 dcy

stealth address amount amount idx
00: f6a5a61f7470a252eebaa68b56d3a6d62e50cc7be22283a94961971f57b5b49e 50.110407934000 679701 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": 328394, "vin": [ { "gen": { "height": 328384 } } ], "vout": [ { "amount": 50110407934, "target": { "key": "f6a5a61f7470a252eebaa68b56d3a6d62e50cc7be22283a94961971f57b5b49e" } } ], "extra": [ 1, 82, 233, 128, 149, 198, 49, 87, 59, 112, 23, 251, 241, 167, 121, 207, 228, 254, 163, 173, 167, 21, 21, 76, 206, 142, 217, 207, 183, 199, 58, 89, 4, 2, 17, 0, 0, 0, 19, 112, 98, 232, 230, 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