Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bd71d52604551d850d7e115801b689def282b6e2286843bc3dc5784cad468b5

Tx prefix hash: 484df5e3b5f5f62648689dd8fc03ce5cf6ec76fb21f1be294e8570403a9f0b7f
Tx public key: 3285d548a61b7f44c0596d5429c6e2a9a7738ce2e19eb7acddfe11db5ce862f3
Timestamp: 1754914085 Timestamp [UCT]: 2025-08-11 12:08:05 Age [y:d:h:m:s]: 00:108:17:49:08
Block: 1344791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76984 RingCT/type: yes/0
Extra: 013285d548a61b7f44c0596d5429c6e2a9a7738ce2e19eb7acddfe11db5ce862f30211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e28b1e20a53f423b350fa835ce806fcee9967b963da67fa8a6cae00607b3257 0.600000000000 1832676 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": 1344801, "vin": [ { "gen": { "height": 1344791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e28b1e20a53f423b350fa835ce806fcee9967b963da67fa8a6cae00607b3257" } } ], "extra": [ 1, 50, 133, 213, 72, 166, 27, 127, 68, 192, 89, 109, 84, 41, 198, 226, 169, 167, 115, 140, 226, 225, 158, 183, 172, 221, 254, 17, 219, 92, 232, 98, 243, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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