Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25eb55c6a78309081b5661b1e0f41647a96d203e9b57e98a1b1816b78a46d86f

Tx prefix hash: e2a2774814c901ebba8a11d04309fdfe8cda001c939cfeb98be13c3aac825fa6
Tx public key: 9f4541e3cf818f56240c54369e47a0c67416e88504d3cc5221cf89f8d0d4f633
Timestamp: 1744291580 Timestamp [UCT]: 2025-04-10 13:26:20 Age [y:d:h:m:s]: 00:218:07:14:03
Block: 1258444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153749 RingCT/type: yes/0
Extra: 019f4541e3cf818f56240c54369e47a0c67416e88504d3cc5221cf89f8d0d4f633021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3c99ffa0f5dd8ab291327cbaf122782e6e59f4e2eee869ca97ca2eea3102d71 0.600000000000 1745577 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": 1258454, "vin": [ { "gen": { "height": 1258444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3c99ffa0f5dd8ab291327cbaf122782e6e59f4e2eee869ca97ca2eea3102d71" } } ], "extra": [ 1, 159, 69, 65, 227, 207, 129, 143, 86, 36, 12, 84, 54, 158, 71, 160, 198, 116, 22, 232, 133, 4, 211, 204, 82, 33, 207, 137, 248, 208, 212, 246, 51, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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