Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42526e3ee4fb003326c53f24c1cc3818c81f13ca18aaa9a9733b5a56cdd4ee38

Tx prefix hash: 3ce843edb62f8dcffaafece4e9c735f9307e002dbc3f3792c07f213dabdd28e0
Tx public key: dd54dd0f66fb964418e5335101792a99a395fd688485bad480c2cd22ecdcb28e
Timestamp: 1715805826 Timestamp [UCT]: 2024-05-15 20:43:46 Age [y:d:h:m:s]: 00:324:17:13:33
Block: 1022787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232093 RingCT/type: yes/0
Extra: 01dd54dd0f66fb964418e5335101792a99a395fd688485bad480c2cd22ecdcb28e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abaa4f9ea1d58f3b0f0e2125e63419a097ed1bc8a2c929b25a7db999bf3c5ff3 0.600000000000 1487488 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": 1022797, "vin": [ { "gen": { "height": 1022787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abaa4f9ea1d58f3b0f0e2125e63419a097ed1bc8a2c929b25a7db999bf3c5ff3" } } ], "extra": [ 1, 221, 84, 221, 15, 102, 251, 150, 68, 24, 229, 51, 81, 1, 121, 42, 153, 163, 149, 253, 104, 132, 133, 186, 212, 128, 194, 205, 34, 236, 220, 178, 142, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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