Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b7483a885bf7ae8aebece69011dbe021b7f8b227a30fb893affd995e4c9fb7

Tx prefix hash: 934f36cfbeb67bb4bdab3e4da617ef05000fe3c6b6e2b5cbcae37f2d4205cdcc
Tx public key: 2431bb7cf9a7b8e9ac0f1fb451e93a80a4c801d4aea62f8eee0212b9d443aaa0
Timestamp: 1750829340 Timestamp [UCT]: 2025-06-25 05:29:00 Age [y:d:h:m:s]: 00:146:17:45:37
Block: 1312319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102806 RingCT/type: yes/0
Extra: 012431bb7cf9a7b8e9ac0f1fb451e93a80a4c801d4aea62f8eee0212b9d443aaa002110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99df947cb68d3646e3cbe323784a1cda185a6ad93e86bed788537f9b0ab4e5a6 0.600000000000 1799952 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": 1312329, "vin": [ { "gen": { "height": 1312319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99df947cb68d3646e3cbe323784a1cda185a6ad93e86bed788537f9b0ab4e5a6" } } ], "extra": [ 1, 36, 49, 187, 124, 249, 167, 184, 233, 172, 15, 31, 180, 81, 233, 58, 128, 164, 200, 1, 212, 174, 166, 47, 142, 238, 2, 18, 185, 212, 67, 170, 160, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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