Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9224e6eba0cd747960971b5f744c0f8647979f407de42b6f37498f3ea359f36e

Tx prefix hash: 18f74db3f078025f67028ea52183832479a80fc2525cc17f153b8eef3cb5a245
Tx public key: 719e9fa3d5c54dbe92a69b7e76d34002a15e44995d70dcaf7fda7eb91e997691
Timestamp: 1712576546 Timestamp [UCT]: 2024-04-08 11:42:26 Age [y:d:h:m:s]: 01:067:23:44:57
Block: 995990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309512 RingCT/type: yes/0
Extra: 01719e9fa3d5c54dbe92a69b7e76d34002a15e44995d70dcaf7fda7eb91e99769102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 630ce80ba3b7394b4dd343b93b856aa90eeb2f6ad40bf2d1c1ca1e5b4ce4674d 0.600000000000 1456406 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": 996000, "vin": [ { "gen": { "height": 995990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "630ce80ba3b7394b4dd343b93b856aa90eeb2f6ad40bf2d1c1ca1e5b4ce4674d" } } ], "extra": [ 1, 113, 158, 159, 163, 213, 197, 77, 190, 146, 166, 155, 126, 118, 211, 64, 2, 161, 94, 68, 153, 93, 112, 220, 175, 127, 218, 126, 185, 30, 153, 118, 145, 2, 17, 0, 0, 0, 1, 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