Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deea7566263e8fcab28319c57561fc8ad271cae1deaa671b645f1f8f0dd0958b

Tx prefix hash: 29cfa1f1bb24de666461eb04edc110e03e69df2c4d55e8f297280c9e3d64916f
Tx public key: 0a422c443b0cd3af60c7a56cfeba334c1d184cd08cfa8a286ee6d45c18716072
Timestamp: 1719260985 Timestamp [UCT]: 2024-06-24 20:29:45 Age [y:d:h:m:s]: 00:325:04:17:46
Block: 1051417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232396 RingCT/type: yes/0
Extra: 010a422c443b0cd3af60c7a56cfeba334c1d184cd08cfa8a286ee6d45c187160720211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f5b759521d492621cbb4571790af6997593f33ea6eb9ffde7c5486ceca26c3a 0.600000000000 1521728 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": 1051427, "vin": [ { "gen": { "height": 1051417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f5b759521d492621cbb4571790af6997593f33ea6eb9ffde7c5486ceca26c3a" } } ], "extra": [ 1, 10, 66, 44, 68, 59, 12, 211, 175, 96, 199, 165, 108, 254, 186, 51, 76, 29, 24, 76, 208, 140, 250, 138, 40, 110, 230, 212, 92, 24, 113, 96, 114, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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