Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00ccbba1174073c2f4d6059ad16f8003afd3e136a5af898450577b9d7e5630ae

Tx prefix hash: 27e5c45ddb476c7614dd10eac23d86349ec41fff1f466b780f001e08a124a2f7
Tx public key: b54843a236cf5b913725963a1c0cce38c2d2146a6d6508850cc9bbb5e9ef01a3
Timestamp: 1750398317 Timestamp [UCT]: 2025-06-20 05:45:17 Age [y:d:h:m:s]: 00:201:06:36:10
Block: 1308868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141741 RingCT/type: yes/0
Extra: 01b54843a236cf5b913725963a1c0cce38c2d2146a6d6508850cc9bbb5e9ef01a3021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe466afd2e45b761226e83e3e59215a8b5c907f9b1c68b3e48e78e1669c3a52f 0.600000000000 1796483 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": 1308878, "vin": [ { "gen": { "height": 1308868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe466afd2e45b761226e83e3e59215a8b5c907f9b1c68b3e48e78e1669c3a52f" } } ], "extra": [ 1, 181, 72, 67, 162, 54, 207, 91, 145, 55, 37, 150, 58, 28, 12, 206, 56, 194, 210, 20, 106, 109, 101, 8, 133, 12, 201, 187, 181, 233, 239, 1, 163, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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