Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4baa42113cb038ed589e1b16e5452b279971a92c916c1dcee35c59faf1353100

Tx prefix hash: f4d822f5d292b5fa0b0ff68c3dc1642997d28516c7225615b055c419f79dde48
Tx public key: 627e4d8e61ae4978e884e5cace909ad40bdab393a45bef0abfa86b6d0c3c60f9
Timestamp: 1744919205 Timestamp [UCT]: 2025-04-17 19:46:45 Age [y:d:h:m:s]: 00:216:11:04:09
Block: 1263630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152436 RingCT/type: yes/0
Extra: 01627e4d8e61ae4978e884e5cace909ad40bdab393a45bef0abfa86b6d0c3c60f9021100000014dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da83e133356d5c79994e7319dfe25a8b7f6bea26c94da371d4fdc20412b461a7 0.600000000000 1750821 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": 1263640, "vin": [ { "gen": { "height": 1263630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da83e133356d5c79994e7319dfe25a8b7f6bea26c94da371d4fdc20412b461a7" } } ], "extra": [ 1, 98, 126, 77, 142, 97, 174, 73, 120, 232, 132, 229, 202, 206, 144, 154, 212, 11, 218, 179, 147, 164, 91, 239, 10, 191, 168, 107, 109, 12, 60, 96, 249, 2, 17, 0, 0, 0, 20, 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