Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22a069a9718e621e9a93278e55b43ed6faa9cd0d49ee42e5b219ccf0fa2352b3

Tx prefix hash: 9ab497720ea62623bc41ef1a6b791f44c9ecee5cd32e9a8337714009a1c27c01
Tx public key: a46cd677739d876c1f1b637fac3ecd58e443bc6e351e8d9b36db3d44816fd9e3
Timestamp: 1718340835 Timestamp [UCT]: 2024-06-14 04:53:55 Age [y:d:h:m:s]: 00:273:04:56:40
Block: 1043806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195238 RingCT/type: yes/0
Extra: 01a46cd677739d876c1f1b637fac3ecd58e443bc6e351e8d9b36db3d44816fd9e302110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85576bb4e9bc48602d4ba0d9c53be59f67a0a8d38704465e9c7ef49c600f7986 0.600000000000 1512965 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": 1043816, "vin": [ { "gen": { "height": 1043806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85576bb4e9bc48602d4ba0d9c53be59f67a0a8d38704465e9c7ef49c600f7986" } } ], "extra": [ 1, 164, 108, 214, 119, 115, 157, 135, 108, 31, 27, 99, 127, 172, 62, 205, 88, 228, 67, 188, 110, 53, 30, 141, 155, 54, 219, 61, 68, 129, 111, 217, 227, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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