Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30d68b19cb6078dff5bc94b3157fc0b0bc803e678fb46c1198c4b02ce5063b42

Tx prefix hash: 773c84388dbdac386e25685991490008ba442c07d2f49a2a62cc175a52263d3a
Tx public key: 4b617b51c9aa904620361c1183565ae925ea1e2c1df7d543323a9222e01b373c
Timestamp: 1733437348 Timestamp [UCT]: 2024-12-05 22:22:28 Age [y:d:h:m:s]: 00:101:13:14:56
Block: 1168858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72390 RingCT/type: yes/0
Extra: 014b617b51c9aa904620361c1183565ae925ea1e2c1df7d543323a9222e01b373c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afbf467f4abcc57d4fa75bab854bcf628d3c4ba6dabfd4b8a5cf0369bb12755a 0.600000000000 1654569 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": 1168868, "vin": [ { "gen": { "height": 1168858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afbf467f4abcc57d4fa75bab854bcf628d3c4ba6dabfd4b8a5cf0369bb12755a" } } ], "extra": [ 1, 75, 97, 123, 81, 201, 170, 144, 70, 32, 54, 28, 17, 131, 86, 90, 233, 37, 234, 30, 44, 29, 247, 213, 67, 50, 58, 146, 34, 224, 27, 55, 60, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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