Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97d75a2fcd66922ec9252a050c353d2383bb14e34d906fa6064fd9f4e70d3b4c

Tx prefix hash: e658ca49d49b72cf19d3dbd81e56654ba1a897f68c5e05e8351fc625f3dcd760
Tx public key: fcd82963fb387c0bb3ae6e51d97ee3c5951eb14e0566fda0af54ebc1353c99fe
Timestamp: 1715942310 Timestamp [UCT]: 2024-05-17 10:38:30 Age [y:d:h:m:s]: 00:312:12:28:55
Block: 1023916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223367 RingCT/type: yes/0
Extra: 01fcd82963fb387c0bb3ae6e51d97ee3c5951eb14e0566fda0af54ebc1353c99fe02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbb62266428f36832c3a4b6e6925cd1f6bf84ac309d148d098c43fd11b71ad02 0.600000000000 1489255 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": 1023926, "vin": [ { "gen": { "height": 1023916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbb62266428f36832c3a4b6e6925cd1f6bf84ac309d148d098c43fd11b71ad02" } } ], "extra": [ 1, 252, 216, 41, 99, 251, 56, 124, 11, 179, 174, 110, 81, 217, 126, 227, 197, 149, 30, 177, 78, 5, 102, 253, 160, 175, 84, 235, 193, 53, 60, 153, 254, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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