Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48b0ff53d63ae662f194f1f8ca4a0e990118ecc3eb26491e9c72940a4c863e92

Tx prefix hash: ca8ca9d16cd9ed6609fb91ca754db0300701c07efa0a90a81a0fe64c46562ac7
Tx public key: 865b30e36d1f027173166596d08173593a07b59653dc6a2014b0c1201c7b1396
Timestamp: 1707981658 Timestamp [UCT]: 2024-02-15 07:20:58 Age [y:d:h:m:s]: 01:051:14:28:05
Block: 957913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297904 RingCT/type: yes/0
Extra: 01865b30e36d1f027173166596d08173593a07b59653dc6a2014b0c1201c7b139602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5848d9e50d7c910fa6e4e7c70729f6a23295e3a53880a3b161d97d62a6f9cd52 0.600000000000 1417264 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": 957923, "vin": [ { "gen": { "height": 957913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5848d9e50d7c910fa6e4e7c70729f6a23295e3a53880a3b161d97d62a6f9cd52" } } ], "extra": [ 1, 134, 91, 48, 227, 109, 31, 2, 113, 115, 22, 101, 150, 208, 129, 115, 89, 58, 7, 181, 150, 83, 220, 106, 32, 20, 176, 193, 32, 28, 123, 19, 150, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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