Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48e0a5dac871b62394abd0dbaf9f7171b71f547dfa0dd3d86374df0bd385a72b

Tx prefix hash: bf17507d433804721591454c3fbf7d07d04c93f2fff88a3603979dd897afb8b6
Tx public key: 99d52722de98b6613bb9a042464df40efc8fca1c68f5fbd827afe547e388ce85
Timestamp: 1746800250 Timestamp [UCT]: 2025-05-09 14:17:30 Age [y:d:h:m:s]: 00:264:19:30:50
Block: 1279208 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186898 RingCT/type: yes/0
Extra: 0199d52722de98b6613bb9a042464df40efc8fca1c68f5fbd827afe547e388ce850211000000011f90517a000000000000000000

1 output(s) for total of 0.600010000000 dcy

stealth address amount amount idx
00: ffbfed71ba51b802b6b2d04fbf7f77e9a89bb0b4ab3feaf700eaa6384c54afcb 0.600010000000 1766581 of 0

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": 1279218, "vin": [ { "gen": { "height": 1279208 } } ], "vout": [ { "amount": 600010000, "target": { "key": "ffbfed71ba51b802b6b2d04fbf7f77e9a89bb0b4ab3feaf700eaa6384c54afcb" } } ], "extra": [ 1, 153, 213, 39, 34, 222, 152, 182, 97, 59, 185, 160, 66, 70, 77, 244, 14, 252, 143, 202, 28, 104, 245, 251, 216, 39, 175, 229, 71, 227, 136, 206, 133, 2, 17, 0, 0, 0, 1, 31, 144, 81, 122, 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