Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ce90558ef220dbe9fd1e35267bd65f8d4c55dc859cf9411431e97eed6340a5

Tx prefix hash: fdf94e5a2026fea7cfea31fa451509cb997e7d461d4d413c7be18477f7993b8c
Tx public key: 0f183f05879343b327684acb4f21c77fc25c0b1a9a595d69220ca17c2da183a5
Timestamp: 1749985744 Timestamp [UCT]: 2025-06-15 11:09:04 Age [y:d:h:m:s]: 00:151:17:36:54
Block: 1305488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106224 RingCT/type: yes/0
Extra: 010f183f05879343b327684acb4f21c77fc25c0b1a9a595d69220ca17c2da183a5021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22057c23f70a756b35fc14bc86ee4018b59619d528fe9c41cc486ff1f92ad8a8 0.600000000000 1793089 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": 1305498, "vin": [ { "gen": { "height": 1305488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22057c23f70a756b35fc14bc86ee4018b59619d528fe9c41cc486ff1f92ad8a8" } } ], "extra": [ 1, 15, 24, 63, 5, 135, 147, 67, 179, 39, 104, 74, 203, 79, 33, 199, 127, 194, 92, 11, 26, 154, 89, 93, 105, 34, 12, 161, 124, 45, 161, 131, 165, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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