Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb44b541ddf84ff4bbd4667cf9613611c62aceb0fd74541287012f6a74d793d3

Tx prefix hash: 8371b9db908be2df26959b8adf8ee179d8be9b51024da023aca9a89faab60158
Tx public key: 78bba9b126609c822f3e9518eb4f3d5e93a35c6a624c0065efb35c6cf0ffc3a6
Timestamp: 1763102139 Timestamp [UCT]: 2025-11-14 06:35:39 Age [y:d:h:m:s]: 00:054:11:58:15
Block: 1411770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39032 RingCT/type: yes/0
Extra: 0178bba9b126609c822f3e9518eb4f3d5e93a35c6a624c0065efb35c6cf0ffc3a6021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b5c59c0928e5cec4313a0eca4395aafafef81ed9226b6455a40e6a15387edee 0.600000000000 1900233 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": 1411780, "vin": [ { "gen": { "height": 1411770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b5c59c0928e5cec4313a0eca4395aafafef81ed9226b6455a40e6a15387edee" } } ], "extra": [ 1, 120, 187, 169, 177, 38, 96, 156, 130, 47, 62, 149, 24, 235, 79, 61, 94, 147, 163, 92, 106, 98, 76, 0, 101, 239, 179, 92, 108, 240, 255, 195, 166, 2, 17, 0, 0, 0, 2, 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