Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b064874dd0d2a4a8750270428aa40d64625a3a09d971efc924e249ebce48d435

Tx prefix hash: f6005af3ebab14492d4e301812969851ad143911cd99cfaeda8da18f3aa46d57
Tx public key: 4c7b5037ea82a9bcc6af964942fba86d1862d1e0d919f93521d4207ea1b4ec51
Timestamp: 1762907640 Timestamp [UCT]: 2025-11-12 00:34:00 Age [y:d:h:m:s]: 00:009:03:54:04
Block: 1410157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6543 RingCT/type: yes/0
Extra: 014c7b5037ea82a9bcc6af964942fba86d1862d1e0d919f93521d4207ea1b4ec51021100000007d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1375bc0245844e10c0c11c6e6828e5a9df538f3c277026496a5fc84cf018cd6f 0.600000000000 1898606 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": 1410167, "vin": [ { "gen": { "height": 1410157 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1375bc0245844e10c0c11c6e6828e5a9df538f3c277026496a5fc84cf018cd6f" } } ], "extra": [ 1, 76, 123, 80, 55, 234, 130, 169, 188, 198, 175, 150, 73, 66, 251, 168, 109, 24, 98, 209, 224, 217, 25, 249, 53, 33, 212, 32, 126, 161, 180, 236, 81, 2, 17, 0, 0, 0, 7, 216, 231, 210, 65, 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