Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5763364df2f92b3c1633830b6aa1ca6021bc7ce01dbb4b5d8f4104b5e796d922

Tx prefix hash: 44946ba14125ebdc6fb548f8b1c1bcfb2eb25153a5fc63e75f3cefa27dfa5fbf
Tx public key: af8fef41543590ef9cb418c3423049caebfead137aec024f7f0a2afe86a3593c
Timestamp: 1712939931 Timestamp [UCT]: 2024-04-12 16:38:51 Age [y:d:h:m:s]: 00:225:14:44:06
Block: 999005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161528 RingCT/type: yes/0
Extra: 01af8fef41543590ef9cb418c3423049caebfead137aec024f7f0a2afe86a3593c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a39ec8eb9cb4052a610330ad3321baae0adfc4c755dbd1cfd402369f71c7c853 0.600000000000 1459481 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": 999015, "vin": [ { "gen": { "height": 999005 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a39ec8eb9cb4052a610330ad3321baae0adfc4c755dbd1cfd402369f71c7c853" } } ], "extra": [ 1, 175, 143, 239, 65, 84, 53, 144, 239, 156, 180, 24, 195, 66, 48, 73, 202, 235, 254, 173, 19, 122, 236, 2, 79, 127, 10, 42, 254, 134, 163, 89, 60, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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