Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ee2f252f66c89d4d49799cb3c26d048259fb4a435bb2ee09055fa8dbcb0b9c6

Tx prefix hash: c345a0287ca008a5b3632d646e081a33c183d831e0fbbf10ff70a93d635d86a9
Tx public key: fa48622432b5a18d96d932ed447f6f9388a3eef4b455f5f92c62018800b60094
Timestamp: 1721231396 Timestamp [UCT]: 2024-07-17 15:49:56 Age [y:d:h:m:s]: 00:268:03:28:22
Block: 1067772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191568 RingCT/type: yes/0
Extra: 01fa48622432b5a18d96d932ed447f6f9388a3eef4b455f5f92c62018800b6009402110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a22cc08a071cfe178f17f71c57194efb2660a25d4c554f21be01cae3ff6fecd 0.600000000000 1538681 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": 1067782, "vin": [ { "gen": { "height": 1067772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a22cc08a071cfe178f17f71c57194efb2660a25d4c554f21be01cae3ff6fecd" } } ], "extra": [ 1, 250, 72, 98, 36, 50, 181, 161, 141, 150, 217, 50, 237, 68, 127, 111, 147, 136, 163, 238, 244, 180, 85, 245, 249, 44, 98, 1, 136, 0, 182, 0, 148, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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