Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9375e93bfbbab54889f5879e15f0ecb7c554f331829f6b65d595452fcf7b4a1

Tx prefix hash: 71532fd75b7d07cb441b1ecd21cc2a84e4961fc149b38551fdc73b267deda1ba
Tx public key: 329afcf2b5fcb349c37b06485165bcca2c95bb91094b6573e35d0cb2fc6b3f5d
Timestamp: 1723612046 Timestamp [UCT]: 2024-08-14 05:07:26 Age [y:d:h:m:s]: 00:260:23:44:34
Block: 1087504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186422 RingCT/type: yes/0
Extra: 01329afcf2b5fcb349c37b06485165bcca2c95bb91094b6573e35d0cb2fc6b3f5d021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 820964030890fd300d1f623b77e58f8a2037a458f50b795e59d85037e9ceef93 0.600000000000 1562113 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": 1087514, "vin": [ { "gen": { "height": 1087504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "820964030890fd300d1f623b77e58f8a2037a458f50b795e59d85037e9ceef93" } } ], "extra": [ 1, 50, 154, 252, 242, 181, 252, 179, 73, 195, 123, 6, 72, 81, 101, 188, 202, 44, 149, 187, 145, 9, 75, 101, 115, 227, 93, 12, 178, 252, 107, 63, 93, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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