Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ad37190a78f38f6933186166be4259211da9ff27b5a264e621e6d13f0db94f3

Tx prefix hash: 03948985d519a6f45da34111287a33a849da54fb014e49f0a31e6006a51b4bed
Tx public key: f383d340cb8f6140f6bacb9ca59bf830e701f197f4cff5da60f6fc0c551d9026
Timestamp: 1755959200 Timestamp [UCT]: 2025-08-23 14:26:40 Age [y:d:h:m:s]: 00:086:05:20:32
Block: 1352747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61565 RingCT/type: yes/0
Extra: 01f383d340cb8f6140f6bacb9ca59bf830e701f197f4cff5da60f6fc0c551d90260211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cb82a93418d0d689e1c9e04120a8ff539ae6f4811c017fcae37db2c1c020bf3 0.600000000000 1840714 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": 1352757, "vin": [ { "gen": { "height": 1352747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cb82a93418d0d689e1c9e04120a8ff539ae6f4811c017fcae37db2c1c020bf3" } } ], "extra": [ 1, 243, 131, 211, 64, 203, 143, 97, 64, 246, 186, 203, 156, 165, 155, 248, 48, 231, 1, 241, 151, 244, 207, 245, 218, 96, 246, 252, 12, 85, 29, 144, 38, 2, 17, 0, 0, 0, 4, 38, 9, 179, 160, 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