Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d46e789beb0b9cd56848ae818fa722dd0d8a0e92613cbb4e76fac74f2cb249e

Tx prefix hash: 9d660bebefab6457d4574090010dd06147b7ea00b18abad1c0471e3aec5dc403
Tx public key: 86af44ff68d8b52d55ece516f5fc25ce72604837a3d531417c2e46c317b396d2
Timestamp: 1719572774 Timestamp [UCT]: 2024-06-28 11:06:14 Age [y:d:h:m:s]: 00:301:08:59:22
Block: 1054013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215364 RingCT/type: yes/0
Extra: 0186af44ff68d8b52d55ece516f5fc25ce72604837a3d531417c2e46c317b396d202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05cc41af5db73d0bfb3c98a5e94493b674c0a7ef4a4e9637fc8a500144ec8fa4 0.600000000000 1524372 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": 1054023, "vin": [ { "gen": { "height": 1054013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05cc41af5db73d0bfb3c98a5e94493b674c0a7ef4a4e9637fc8a500144ec8fa4" } } ], "extra": [ 1, 134, 175, 68, 255, 104, 216, 181, 45, 85, 236, 229, 22, 245, 252, 37, 206, 114, 96, 72, 55, 163, 213, 49, 65, 124, 46, 70, 195, 23, 179, 150, 210, 2, 17, 0, 0, 0, 6, 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