Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30c1d6338a08fec0db4051c1221b927247192d9d4a665ceedaa637dc7655bafb

Tx prefix hash: 538a0b61d7869e90876794038607f9f4df127662e5e5aed958f1379ef12092b4
Tx public key: 25d4a0c02adbadc75cc3738ed76e516df4bd32c6e0efb171892fd4117258af19
Timestamp: 1644987244 Timestamp [UCT]: 2022-02-16 04:54:04 Age [y:d:h:m:s]: 02:133:16:07:21
Block: 439639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 614666 RingCT/type: yes/0
Extra: 0125d4a0c02adbadc75cc3738ed76e516df4bd32c6e0efb171892fd4117258af19021100000002cb8520c2000000000000000000

1 output(s) for total of 21.443406776000 dcy

stealth address amount amount idx
00: dd5f30f957e069fa08c9ac4ade6926335dc93d11f7b4521f43e4b6e11329e30b 21.443406776000 851802 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": 439649, "vin": [ { "gen": { "height": 439639 } } ], "vout": [ { "amount": 21443406776, "target": { "key": "dd5f30f957e069fa08c9ac4ade6926335dc93d11f7b4521f43e4b6e11329e30b" } } ], "extra": [ 1, 37, 212, 160, 192, 42, 219, 173, 199, 92, 195, 115, 142, 215, 110, 81, 109, 244, 189, 50, 198, 224, 239, 177, 113, 137, 47, 212, 17, 114, 88, 175, 25, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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