Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59b506eeb5edaafbbb6dff69217989e333186efac935d54de4b315033b56c69c

Tx prefix hash: 2fb4d1247c135435bc7d0236070a7d11a452a67372756d5189eac2a1a945a54d
Tx public key: 7b1af9063eeab29454a01f34c230e1d7daaad296d521c703b3e5e0abc9359212
Timestamp: 1718299417 Timestamp [UCT]: 2024-06-13 17:23:37 Age [y:d:h:m:s]: 00:224:04:48:33
Block: 1043453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160401 RingCT/type: yes/0
Extra: 017b1af9063eeab29454a01f34c230e1d7daaad296d521c703b3e5e0abc93592120211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be4278fffb61075583c31cd0f29e5fa5a30d09650926f864d67b2e31e3a7c3ea 0.600000000000 1512606 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": 1043463, "vin": [ { "gen": { "height": 1043453 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be4278fffb61075583c31cd0f29e5fa5a30d09650926f864d67b2e31e3a7c3ea" } } ], "extra": [ 1, 123, 26, 249, 6, 62, 234, 178, 148, 84, 160, 31, 52, 194, 48, 225, 215, 218, 170, 210, 150, 213, 33, 199, 3, 179, 229, 224, 171, 201, 53, 146, 18, 2, 17, 0, 0, 0, 3, 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